Skip to content

Add infrastructure for validating JSON schemas #2073

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

Add infrastructure for validating JSON schemas #2073

wants to merge 1 commit into from

Conversation

per1234
Copy link
Contributor

@per1234 per1234 commented Feb 13, 2023

Please check if the PR fulfills these requirements

See how to contribute

  • The PR has no duplicates (please search among the Pull Requests
    before creating one)
  • The PR follows
    our contributing guidelines
  • [N/A] Tests for the changes have been added (for bug fixes / features)
  • [N/A] Docs have been added / updated (for bug fixes / features)
  • [N/A] UPGRADING.md has been updated with a migration guide (for breaking changes)

What kind of change does this PR introduce?

Infrastructure enhancement

What is the current behavior?

There is no validation of the Arduino CLI configuration file JSON schema. This will increase the burden on contributors to the schema and the reviewers of those contributions.

What is the new behavior?

A task and GitHub Actions workflow is added here to validate JSON schema files against the meta-schema.

On every push or pull request that affects the repository's JSON schema files, and periodically, the workflow will automatically validate the schemas.

The workflow is designed to allow expansion to validation of any number of JSON schemas that might be added to the repository in the future (we had some tentative plans to move the schemas from the Arduino Lint repository to this repo).

Does this PR introduce a breaking change, and is titled accordingly?

No breaking change.

A task and GitHub Actions workflow is added here to validate JSON schema files against the meta-schema.

On every push or pull request that affects the repository's JSON schema files, and periodically, the workflow will
automatically validate the schemas.
@per1234 per1234 added type: enhancement Proposed improvement topic: infrastructure Related to project infrastructure labels Feb 13, 2023
@per1234 per1234 requested a review from Bikappa February 13, 2023 16:59
@per1234 per1234 self-assigned this Feb 13, 2023
@codecov
Copy link

codecov bot commented Feb 13, 2023

Codecov Report

Base: 36.66% // Head: 36.68% // Increases project coverage by +0.01% 🎉

Coverage data is based on head (3d23000) compared to base (b967fe4).
Patch has no changes to coverable lines.

Additional details and impacted files
@@                  Coverage Diff                  @@
##           chore/json-schema    #2073      +/-   ##
=====================================================
+ Coverage              36.66%   36.68%   +0.01%     
=====================================================
  Files                    228      228              
  Lines                  19385    19385              
=====================================================
+ Hits                    7108     7111       +3     
+ Misses                 11444    11442       -2     
+ Partials                 833      832       -1     
Flag Coverage Δ
unit 36.68% <ø> (+0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
commands/lib/search.go 92.10% <0.00%> (+3.94%) ⬆️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

@Bikappa Bikappa force-pushed the chore/json-schema branch 3 times, most recently from 34c68ce to 99eb639 Compare February 16, 2023 13:02
@per1234
Copy link
Contributor Author

per1234 commented Feb 22, 2023

Superseded by Go-based validation added as part of #2073

@per1234 per1234 closed this Feb 22, 2023
@per1234 per1234 added the conclusion: duplicate Has already been submitted label Feb 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
conclusion: duplicate Has already been submitted topic: infrastructure Related to project infrastructure type: enhancement Proposed improvement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant